| CA Technologies |
3.0 Third-Party Software Compatibility
3.1 Compatibility with CA Aion Previous Releases
4.0 Limitations of Aion in 64-bit Linux/UNIX Environments
5.0 Uninstallation Messages in Console Mode
6.0 Installation Considerations
6.2.1 Silent Installation with Default Settings
6.2.2 Silent Installation using a Response File
6.3 Linux/Unix Product Configuration
8.0 Online Help – Default integer size 64-bits
Welcome to CA Aion Business Rules Expert (CA Aion) r11.0 build 11.0.0.500. This build 11.0 is an upgrade of CA Aion r11.0 and enabling execution in 64-bit native mode in Linux/UNIX environments. This document contains operating system support and known issues for CA Aion r11.0 64-bit processing. For documentation updates, contact CA Support at http://ca.com/support. Use the Support link to access the latest documentation.
Note: Throughout this document, the directory in which CA Aion r11.0 is installed is referred to as <aion_install_dir>.
This section describes operating system support for CA Aion 11.00 64-bit processing. This build supports the RHEL 6u2 Linux 64-bit operating system only for compiling and deploying components written using Aion BRE.
The CA Aion Interactive Development Environment (IDE) and Debugger are only available with CA Aion 11.0 on the following Microsoft Windows platforms:
Note: For more information about product installation and uninstall, see Documentation Changes.
The following hardware and software requirements must be met before installing CA Aion r11.0 for 64-bit.
For CA Aion r11.0 for 64-bit the minimum hardware requirements are:
CA Aion r11.0 64-bit supports the following third-party software:
CA Aion BRE r11.0 for 64-bit RHEL 6u2 offers the same operating functionality as CA Aion BRE r11.0 for 32-bit Linux, except that it executes compiled applications, or interprets applications with REEXEC, natively in a 64-bit RHEL 6u2 environment.
CA Aion BRE r11.0 for 64-bit RHEL 6u2 can interoperate with other software that executes natively in 64-bit mode. CA Aion BRE r11.0 for 64-bit RHEL 6u2 cannot interoperate with other software that executes natively in 32-bit mode.
The standard version of CA Aion BRE r11.0 executes natively in 32-bit mode, and can be used to interoperate with other software that executes natively in 32-bit mode. The standard version cannot interoperate with other software that executes natively in 64-bit mode.
CA Aion applications built for Linux/UNIX environments are generally upward-compatible. For example, applications that are built on a lower version of the operating system can run successfully on a higher version, but it is not applicable conversely.
The CA Aion Debugger and Sybase are not supported in CA Aion r11.0 64-bit.
The Microsoft Windows environment is the principal development environment for CA Aion. Development of CA Aion applications should take place on the Microsoft Windows platform using the CA Aion Version 11.0 Integrated Development Environment (IDE). The Microsoft Windows-based IDE provides remote deployment facilities to other platforms, for example, UNIX and the Mainframe (z Series platforms).
Note: To use existing CA Aion Linux applications, restore and rebuild them with the CA Aion BRE r11.0 for 64-bit RHEL 6u2 version.
CA Aion r11.0 uses the Automated License Program (ALP) to verify that the installed version of CA Aion is properly licensed.
ALP products are shipped with a printed certificate representing their license file based on the product and hardware information recorded in our license database. You can obtain 11.0 license keys electronically at http://ca.com/support.
Note: For more information about CA Licensing, see CA ALP License Package Downloads section in the CA Support website.
The following sections describe known issues for CA Aion r11.0 64 bit processing.
The following Aion capabilities are not supported currently in the RHEL 6u2 Linux 64-bit environment:
Note: Tomcat and WebSphere Application Server 8 are supported.
Symptom:
When uninstalling CA Aion in console mode, the following messages are displayed.
Uninstall completed successfully
Some items could not be removed
These messages appear, even if no CA Aion applications were built between installation and uninstallation process of CA Aion.
Solution:
Verify that the installation directory is deleted and ignore the Some items could not be removed message.
The complete list of published bug fixes since the GA version of CA Aion r11.0, and any updated documentation, including updates to this readme can be found through Published Solutions on Support Online at http://ca.com/support.
For the CA Aion r11.0 64-bit only this Readme is provided. CA Aion r11.0 documents are available at http://ca.com/support.
The following functionality revisions were added after the CA Aion r11.0 Online Help and the CA Aion r11.0 User’s Guide were prepared.
In a future release, the CA Aion Product Guide will be updated with the following section that includes information about installing and uninstalling of CA Aion in 64-bit Linux/UNIX environments.
CA Aion can be installed in GUI, Console, and Silent modes. The following sections contain detailed information about each of the installation modes.
GUI installation mode provides the highest level of information and installation guidance through a wizard.
Follow these steps:
sh ./AionBRE_r11.0.0.500_linux64.bin
sudo sh ./AionBRE_r11.0.0.500_linux64.bin
The Introduction dialog appears.
The License Agreement dialog appears.
Note: If you do not accept the terms of License Agreement, the installation process terminates.
The Review Settings dialog appears.
Note: To reset the installation folder to /opt/CA/AionBRE64, click Restore Default Folder. However, if the response file installer.properties exists, click Restore Default Folder to restore the folder to the value defined in the response file.
The installation process starts. When installation is complete, the Install Complete dialog appears.
The CA Aion installation is complete.
In the Console Mode installation, you can use only the keyboard to select values and navigate through installation.
Follow these steps:
sh ./AionBRE_r11.0.0.500_linux64.bin -i console
sudo sh ./AionBRE_r11.0.0.500_linux64.bin -i console
The Introduction message appears.
The License Agreement message appears.
Type Y to accept and continue installation.
Type N to reject and terminate the installation.
The Choose Install Folder message appears.
The Review Settings message appears.
Note: If the response file installer.properties exists in the current directory, pressing Enter restores the folder to the value defined in the file.
The Ready to Install message appears.
The Installation Complete message appears at the end of installation.
The CA Aion installation is complete.
Silent mode enables the installer to run without user interaction. We recommend using Silent mode when you install CA Aion on multiple clients. You can perform Silent Installation in two ways:
To perform silent installation with default settings defined in the installer, log in to the target system, and enter the following command:
sh ./AionBRE_r11.0.0.500_linux64.bin -i silent
sudo sh ./AionBRE_r11.0.0.500_linux64.bin -i silent
The installer installs the product in the directory /opt/CA/AionBRE64.
The CA Aion installation is complete.
The installer retrieves the values for various InstallAnywhere variables from the response file. The following example contains typical content of a response file.
INSTALLER_UI=silent
USER_INSTALL_DIR=/opt/CA/AionBRE64
Note: It will be necessary to create the installer.properties file containing the above information prior to starting the silent installation using a response file. To specify a different installation directory in the response file, open the response file using any text editing program and assign the location to the USER_INSTALL_DIR variable.
To perform silent installation with a response file, log in to the target system and do the following, depending on whether you are using the default response file or a custom response file:
To use the default response file installer.properties do the following:
When the response file is present in the current installation directory, enter the following command:
sh ./AionBRE_r11.0.0.500_linux64.bin -f installer.properties
When the response file is present in a directory other than the current installation directory, enter the following command:
sh ./AionBRE_r11.0.0.500_linux64.bin -f /home/installer.properties
To use a custom response file for example, myresponse.properties do the following:
When the response file is present in the current installation directory, enter the following command:
sh ./AionBRE_r11.0.0.500_linux64.bin -f myresponse.properties
When the response file is present in home directory, enter the following command:
sh ./AionBRE_r11.0.0.500_linux64.bin -f /home/myresponse.properties
The CA Aion installation is complete
Setup the environment by sourcing either the aion.sh or aion.cshrc files according to your site environment. Example scripts are provided in the <aioninstallationdirectory> directory.
The following example assumes that the /opt/CA/AionBRE is equivalent of <aioninstallationdirectory> and the bash script is used.
source /opt/CA/AionBRE/aion.sh
The default uninstallation mode is the same as the installation mode. For example, if you have installed CA Aion through the Console mode then the default uninstallation mode is Console.
Important! The uninstallation process does not delete files that have changed since the installation. This includes any applications that have been rebuilt from source. Directories containing changed files are not deleted.
Follow these steps:
The default installation directory is /opt/CA/AionBRE64/
sh ./UninstallAionBRE
sudo sh ./UninstallAionBRE
The CA Aion is uninstalled.
Note: To override the default uninstallation mode and uninstall CA Aion through the mode of your choice, see the following sections.
To override the default uninstallation mode and uninstall CA Aion in GUI mode:
Follow these steps:
The default installation directory is /opt/CA/AionBRE64/
sh ./UninstallAionBRE -i gui
sudo sh ./UninstallAionBRE -i gui
Note: If your session does not support a graphical user interface, CA Aion is uninstalled in console mode.
The CA Aion is uninstalled.
To override the default uninstallation mode and uninstall CA Aion in console mode:
Follow these steps:
The default installation directory is /opt/CA/AionBRE64/
sh ./UninstallAionBRE -i console
sudo ./UninstallAionBRE -i console
The CA Aion is uninstalled.
To override the default uninstallation mode and uninstall CA Aion in silent mode:
Follow these steps:
The default installation directory is /opt/CA/AionBRE64/
sh ./UninstallAionBRE -i silent
sudo ./UninstallAionBRE -i silent
The CA Aion is uninstalled.
In CA Aion r11.0 64-bit implementations, the default integer size is 64-bits. This differs from the default integer size in CA Aion r11.0 implementations which is 32-bits. If data is read and written using a CA Aion r11.0 64-bit implementation, this difference will be unnoticeable.
In addition, CA Aion r11.0 64-bit applications can read or write 32-bit integers from binary objects instead. This is illustrated in the QSAM example in the <aion_home>/examples/qsam directory. Refer to the following lines
rc = ReadInteger(rec,int,BIN_FMT_INT4)
rc = WriteInteger(rec,trunc(SalaryBonus*100),BIN_FMT_INT4) //length = 4
If the value of the 3rd argument of the ReadInteger/WriteInteger method invocations above is 0, then 64-bit integers will be read or written by default If CA Aion r11.0 were used, then 32-bit integers would be read or written instead.
The content of the OpenBinary Method in the CA Aion r11.0 online help has not been updated to reflect the new ‘IN Length’ parameter. However, details of this new parameter are provided as follows. Updates to the online help will be provided in the future:
OpenBinary Method
Library
SysLib
Owning Class
Binary
Purpose
This external class method creates a binary stream for either reading or writing. It is particularly valuable when interfacing with existing C APIs that require access to complex structures.
When opening for write, the data argument can be used to specify the initial length of the data buffer. When opening for read, the data argument can be used to initialize the data buffer with a buffer from an external routine.
Syntax
OpenBinary(mode, data, length)
Return Value
(Binary class)
|
Argument |
Type |
Description |
|---|---|---|
|
IN mode |
Integer |
Either of the BIN_* constants. BIN_OPEN_READ opens a binary stream for reading. BIN_OPEN_WRITE open a binary stream for writing. |
|
IN data |
Integer |
|
|
IN length |
Integer |
Length of the binary buffer when it is opened for reading. The default length is 0, which is correct when the binary object is opened for writing. |
This chapter documents the changes to existing features for support of 64-bit processing r11.0.
The reexec command no longer supports the -redebug option in the Linux/ UNIX environments. In the current release, no options are supported for the reexec command. Command line arguments can be specified for the CA Aion application that is being interpreted.
If the respawn command encounters invalid definitions, the application is not built and an error code 4 is returned. By default, the respawn command uses all of the following options if no options are specified.
The redev command only pertains to Windows environments.
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.
To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.
Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.